Electronic database and method for forming same

ABSTRACT

Methods and systems for generating an electronic database, the electronic database comprising database elements being organized in a single table, the single table comprising at least four columns, the at least four columns including: a first column for storing identification numbers of the database elements, a second column for storing a numbers of a parent element for database elements being dependent from other database elements, a third column for storing database elements values, a fourth column for storing a code of the in-use datatypes; and at least five rows, the at least five rows including a first row representing a root element, a second row representing a datatype, a third representing a term, a fourth row representing the term&#39;s attribute and a fifth row representing data.

FIELD

The present technology relates to data processing and more precisely toan electronic database and a method of generating an electronicdatabase.

BACKGROUND

U.S. Pat. No. 5,369,761 teaches a system that may be used to enable adatabase administrator to selectively denormalize a databasetransparently to users and programmers. The system keeps a record of themapping between the denormalized fields and the base fields from whichthey are derived. Processors access those recorded links to keep thedatabase self-consistent and to retrieve data from denormalized fieldswhenever possible.

SUMMARY

Embodiments of the present technology have been developed based ondevelopers' appreciation of at least one technical problem associatedwith the prior art solutions.

The present technology arises from an observation made by thedeveloper(s) that prior art solutions do not always provide flexibilityand are subject to unstable functioning due to the direct involvement ofthe user in building the database structure.

The present technology arises from an observation made by thedeveloper(s) that prior art solutions may require the manual setup ofcorrespondence fields between a normalized and a denormalized table, andproviding usability of data manual selection at the cost of additionalcharges for duplicate information storing. This is one of the solutionsfrom one of the fragments of an information system, and this solutiondoes not form a complete system. Furthermore, this solution does notallow working with large quantities of data without additional actionson the architecture of the database: further normalization, creation ofindexes and data parts (segments or partitions).

The present technology arises from an observation made by thedeveloper(s) that a technical problem solved by embodiments of thepresent technology originates from the necessity of generating across-functional database.

The technical result associated with embodiments of the presenttechnology is to improve the reliability of the database reliability byeliminating errors when adding new data and generating queries andreports, as well as reducing the risk of avalanche-type degradation ofperformance due to the lack of necessary indexes when working with largequantities of data (tens and hundred millions of records).

In accordance with a first broad aspect of the present technology, thereis provided an electronic database, the electronic database comprisingdatabase elements being organized as a single table, the single tablecomprising at least four columns, the at least four columns including: afirst column for storing identification numbers of the databaseelements, a second column for storing a numbers of a parent element fordatabase elements being dependent from other database elements, a thirdcolumn for storing database elements values, a fourth column for storinga cods of the in-use datatypes; and at least five rows, the at leastfive rows including a first row representing a root element, a secondrow representing a datatype, a third representing a term, a fourth rowrepresenting the term's attribute, a fifth row representing data.

In some implementations, the single table further comprises a fifthcolumn, the fifth column for storing sequence numbers of elements amongelements with equal dependencies.

In accordance with a second broad aspect of the present technology,there is provided a method for generating an electronic database by adatabase management system, the method executable by an electronicdevice, the method comprising the steps of: organizing, by the databasemanagement system, data in a single table of at least four columns andat least five rows, generating a first row representing a root elementwherein a first column is for storing a first identification number,generating a second row representing a datatype, wherein the firstcolumn is for storing a datatype unique identification number, thedatatype unique identification number being different from the firstidentification number, a third column is for storing an in-use datatypename and a fourth column is for storing a datatype code, generating athird row representing a term, wherein the first column is for storing aterm unique identification number, the third column is for storing aterm name and the fourth column is for storing an in-use datatype code,generating a fourth row representing a term attribute, wherein the firstcolumn is for storing a term attribute's unique identification numberand the second column is for storing a term attribute's parent elementidentification number, the term attribute being dependent on the parentelement, and generating a fifth row representing data, wherein the firstcolumn is for storing a data unique identification number, the secondcolumn is for storing a data parent element identification number, thedata being dependent on the parent element, the third column is forstoring the data and the fourth column is for storing a unique datatypecode.

In some implementations, the method further comprises generating a fifthcolumn, the fifth column for storing sequence numbers of elements amongelements of equal dependency.

In embodiments of the present technology, information is stored in asingle indexed table with a specified number of columns (bars).Consequently, it is not necessary to alter the structure of the databaseby adding or deleting new tables and relations, adding indexes. Thedeveloped and once specified system becomes universal for any user tasksand excludes external interventions thus excluding errors which canoccur during inserting, altering and deletion of data, and also providesreliability and stability.

The universality (versatility) of the specified system combined with theuse of a Web-interface allows hiding technical details of the databaseand internal algorithms of data handling from the user, as well asproviding the possibility of working with a data model by using anunderstandable language for the user: all objects of the subject areaand manipulation of them are described without using applicationsoftware which also helps to improve the usability and the systemreliability as well as its usability.

The specified system of electronic database creation stores all data ina single table which includes five columns. These columns allowdeveloping any structure of data and specify all characteristics of theinformation unit: identifier (physical location), type, parent, valueand order (among elements of this type for this parent). The firstcolumn contains the identification numbers of database elements (ID),the second column contains the identification numbers of parent elementsfor elements with slave dependencies of other elements (Parent ID), thethird column contains the elements' values (Value), the fourth columncontains the code of the record specified in the same table and is usedas type of an element (Type), the fifth column contains sequence numbersof elements among the elements of equal dependencies (Order).

TABLE 1 Appointment Type Description ID Integer Uniquely identifiesParent ID Integer ID parent element's Type Integer ID type of elementValue String Meaning of element Order Integer The order among equalsubordination

The fifth column (Order) is additional and serves to order the selectionon the user's demand

Here are the following indexes constructed for the table:

PRIMARY (ID)—unique index (foreign key);

Type+Value—type and value for indexed search by value;

Parent ID+Type—Parent and Type for searching of an element's propertiesby using of index.

It is necessary to construct another index for high loaded systems:

Type+ID—Type and ID for fast access to the specified datatype.

The indexes specified above are used to accelerate the data selectionfor the needs of the system: metadata collection (data which describesthe structure of data); selection of samples of types with theirproperties and data altering in accordance with the metadata and theuser's commands.

The type of element (Type) is the unique code which identifies theanalogue of the Table—Field combination. The presence of the index ofthis field allows to do searching in limited space: it is not necessaryto view the entire table, it is enough to view only the part of itrelated to the desired table field. FIG. 1 shows how the presence of theindex (Type index) allows to store data compactly and to quicklyretrieve the list of physical addresses of data in data table withoutthe need to view the entire data table.

The definition of data, relations and dependencies are stored in theform of metadata in the same table where the data is.

Each element (data unit) captures at least one table row which consistsof its identification number, parent element identification number,datatype and value. The value is stored as a set of characters by chunksof limited length, for example, of 127 characters. If the field size ofthe third column (Value) is not enough for storing an element's value,the rest of this value will be written to slave elements—rows numberedin order of filling a field for the fifth column (Order). Such rows havea special type (Type) that equals to 0 which is not described inmetadata, but is frequently or regularly used by the system. In case ofthe Order field absence, the fragments of Value ordering are determinedby their ID's sequencing.

Metadata is dependent on nonexistent element with ID=0, independentelements (objects) are dependent on the root element with ID=1.

Metadata describes data structure, the system creates, stores andprocesses data elements in accordance with this structure.

The system understands the base datatypes listed below, as well asallows to create a new base and optional datatypes which inherit basedatatypes properties. The base type uses its own ID as a type. Theoptional type uses relation on the base type or other optional type asthe type.

An example of base datatypes set is shown in Table 2.

TABLE 2 Type Description SHORT A short string (up to 127 characters)CHARS A string of unlimited length MEMO Text (different from CHARS onlymultiline input field) DATE Date DATETIME Date and time FILE File NUMBERInteger SIGNED The number with a decimal part BUTTON Action BOOLEANBoolean (Yes/No)

The base datatypes are used as metadata and identified by the field inthe Value column. For the type identification, in case when this recorddescribes the base type, the metadata's record contains in the Typefield the identifier of the base type or its own type.

Due to a limited and fixed set of the base datatypes properties, theseproperties can be once programmed and used for processing and submissionof data to the user. The set of base datatypes provides the possibilityof generating any degree of complexity of various data structures.

As a datatype, it is possible to use a relation to the identifier of anyexisting non-basic datatype, and this will mean a correspond relation ofthese two datatypes. It enables to describe all kinds of interrelateddatatypes of elements, and each of them will have all kinds ofproperties.

An example of metadata data describing in the database is listed inTable 3.

TABLE 3 Parent Id ID Value (comment) Type Order comment 1 1 Root 1 0Root element, 8 0 CHARS 8 0 Base 9 0 DATE 9 0 datatypes 11 0 BOOLEAN 110 13 0 NUMBER 13 0 15 0 SIGNED 15 0 2 0 Contract 13 0 Terms - 3 0 Client8 0 arbitrary 14 0 (a reference to the 3 0 datatypes Client: Value fieldis empty, and as the type of ID used term, which refers to this type of)4 0 Debit note 13 0 5 0 Total 15 0 18 0 Date 9 0 21 0 Product 8 0 22 0Subject of a contract 8 0 23 0 Price 15 0 24 0 Cost price 15 0 19 2(Data field empty. This 18 1 Term's record captures the fact propertythat the object of the “Contract” (2) have props such as “Date” (18)) 202 (Data field is empty) 22 2 25 2 (Data field is empty) 23 3 26 2 (Thedata field is empty, 14 4 the record sets props “link on the Client(14)” type in the “Contract” (2)) 28 21 (Data field is empty) 23 5 29 21(Data field is empty) 24 6 1181 1 1161 (Contract) 2 1 Data 3561 118120060602 (date) 18 1 3562 1181 Carrying out works . . . 22 2 3563 118140000 (total) 23 3 3565 1181 (A reference to the 113326 4 Client)

This method may be realized as follows.

Applying a DBMS, for example, MySQL, by using the SQL programminglanguage, the aforesaid table is created from the root element's recordin the first row.

Next, the base datatypes are selected in the second and subsequent rowsby binding the unique identification number for the first column ID. Thevalues of cells for the second column Parent ID are being set as nullbecause the elements of types have no parents. The cells of the thirdcolumn Value are being set as names of datatypes. The base datatypes ofcells for the fourth column Type are being set by ID's of them—the basedatatypes refer to themselves as a type. The values of cells for thefifth column Order are being set as null values because of theindependence of these elements and the absence of dependence order.

The next rows describe the terms used by the user for data description.A term can define a link for another term described previously. Thecells of the first column ID contain the unique identification numbersof terms. The cells of the second column Parent ID consist of nullvalues. The cells of the third column Value contain the names of termsor null values in case this term refers??? to another term. The terms ofcells for the fourth column Type consist of code types for this term—IDof the base type or ID of another term described previously in case ifthis term refers?? to another term. The cells of the fifth column Ordercontain null values.

In accordance with the terms, their properties dependent on them aredescribed: parameters or characteristics of the terms are used by theuser for describing data. The cells of the first column ID contain theunique identification numbers of properties. The cells of the secondcolumn Parent ID consist of parents' terms identification numbers. Thecells of the third column Value may store additional operationinformation, for example, default value for this attribute, attribute ofits required presence or mask for checking its validity. The cells ofthe fourth column Type consist of properties type—ID of the elementpreviously described for the identification of purpose andcharacteristics of this term. The cells of the fifth column Ordercontain number values of dependence order among other equal term'sproperties.

Next comes the description of the data which contains semanticinformation for the user and which will be used for reports generatedduring the user's queries processing. The cells of the first column IDcontain the unique identification numbers of data units. The cells ofthe second column Parent ID consist of the root′ identification numberor parent terms if present. The cells of the third column Value storedata values. The cells for the fourth column Type consist of ID for datatype which determines the characteristics of this specific record. Theells of the fifth column Order contain number values of dependence orderin case of presence of several equal elements which are slave to anotherdata element.

It may be understood by a person skilled in the art that the specifiedorder for filling rows and columns is given as an example aimed atdescribing the present technology. The order of rows and columns maydiffer depending on the order of inserting, altering and deletinginformation from a table for each specified case.

In the context of the present specification, SQL (Structured QueryLanguage) is a special-purpose domain-specific language used inprogramming and designed for managing data held in a relational databasemanagement system (RDBMS), or for stream processing in a relational datastream management system.

In the context of the present specification, MySQL is an open-sourcerelational database management system (RDBMS).

In the context of the present specification, an interface is a sharedboundary across which three separate components of a computer systemexchange information.

In the context of the present specification, a database is an organizedcollection of data.

In the context of the present specification, a database managementsystem (DBMS) is a computer software application that interacts with theuser, other applications, and the database itself to capture and analyzedata.

In the context of the present specification, an element (unit) ofdatabase—structural unit, which is the root element, data type, term,term's property or data.

In the context of the present specification, a database index is a datastructure that improves the speed of data retrieval operations on adatabase table at the cost of additional writes and storage space tomaintain the index data structure. Indexes are used to quickly locatedata without having to search every row in a database table every time adatabase table is accessed. Indexes can be created using one or morecolumns of a database table, providing the basis for both rapid randomlookups and efficient access of ordered records.

In the context of the present specification, a “server” is a computerprogram that is running on appropriate hardware and is capable ofreceiving requests (e.g. from electronic devices) over a network, andcarrying out those requests, or causing those requests to be carriedout. The hardware may be implemented as one physical computer or onephysical computer system, but neither is required to be the case withrespect to the present technology. In the present context, the use ofthe expression a “server” is not intended to mean that every task (e.g.received instructions or requests) or any particular task will have beenreceived, carried out, or caused to be carried out, by the same server(i.e. the same software and/or hardware); it is intended to mean thatany number of software elements or hardware devices may be involved inreceiving/sending, carrying out or causing to be carried out any task orrequest, or the consequences of any task or request; and all of thissoftware and hardware may be one server or multiple servers, both ofwhich are included within the expression “at least one server”.

In the context of the present specification, “electronic device” is anycomputer hardware that is capable of running software appropriate to therelevant task at hand. In the context of the present specification, theterm “electronic device” implies that a device can function as a serverfor other electronic devices and electronic devices, however it is notrequired to be the case with respect to the present technology. Thus,some (non-limiting) examples of electronic devices include personalcomputers (desktops, laptops, netbooks, etc.), smartphones, and tablets,as well as network equipment such as routers, switches, and gateways. Itshould be understood, that in the present context the fact that thedevice functions as an electronic device does not mean that it cannotfunction as a server for other electronic devices. The use of theexpression “an electronic device” does not preclude multiple electronicdevices being used in receiving/sending, carrying out or causing to becarried out any task or request, or the consequences of any task orrequest, or steps of any method described herein.

In the context of the present specification, the expression“information” includes information of any nature or kind whatsoevercapable of being stored in a database. Thus information includes, but isnot limited to audiovisual works (images, movies, sound records,presentations etc.), data (location data, numerical data, etc.), text(opinions, comments, questions, messages, etc.), documents,spreadsheets, etc.

In the context of the present specification, the expression “softwarecomponent” is meant to include software (appropriate to a particularhardware context) that is both necessary and sufficient to achieve thespecific function(s) being referenced.

In the context of the present specification, the words “first”,“second”, “third”, etc. have been used as adjectives only for thepurpose of allowing for distinction between the nouns that they modifyfrom one another, and not for the purpose of describing any particularrelationship between those nouns. Thus, for example, it should beunderstood that, the use of the terms “first database” and “thirdserver” is not intended to imply any particular order, type, chronology,hierarchy or ranking (for example) of/between the server, nor is theiruse (by itself) intended imply that any “second server” must necessarilyexist in any given situation. Further, as is discussed herein in othercontexts, reference to a “first” element and a “second” element does notpreclude the two elements from being the same actual real-world element.Thus, for example, in some instances, a “first” server and a “second”server may be the same software and/or hardware components, in othercases they may be different software and/or hardware components.

Implementations of the present technology each have at least one of theabove-mentioned object and/or aspects, but do not necessarily have allof them. It should be understood that some aspects of the presenttechnology that have resulted from attempting to attain theabove-mentioned object may not satisfy this object and/or may satisfyother objects not specifically recited herein.

Additional and/or alternative features, aspects and advantages ofimplementations of the present technology will become apparent from thefollowing description, the accompanying drawings and the appendedclaims.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features, aspects and advantages of the presenttechnology will become better understood with regard to the followingdescription, appended claims and accompanying drawings where:

FIG. 1 is an illustration of a table representation of a type index anddata table.

FIG. 2 is an illustration of a table representation of the

Client

and the

Meeting

data arrays.

FIG. 3 is an illustration of a table representation of the

Contract

data array.

FIG. 4 is an illustration of the view of the editor by the

Types

tab.

FIG. 5 is an illustration of accordance of the editor fields to thetable representation fields.

FIG. 6 is an illustration of the form for the report generation.

FIG. 7 is an illustration of the view of the formed report.

DETAILED DESCRIPTION OF THE DRAWINGS

The examples and conditional language recited herein are principallyintended to aid the reader in understanding the principles of thepresent technology and not to limit its scope to such specificallyrecited examples and conditions. It will be appreciated that thoseskilled in the art may devise various arrangements which, although notexplicitly described or shown herein, nonetheless embody the principlesof the present technology and are included within its spirit and scope.

Furthermore, as an aid to understanding, the following description maydescribe relatively simplified implementations of the presenttechnology. As persons skilled in the art would understand, variousimplementations of the present technology may be of a greatercomplexity.

In some cases, what are believed to be helpful examples of modificationsto the present technology may also be set forth. This is done merely asan aid to understanding, and, again, not to define the scope or setforth the bounds of the present technology. These modifications are notan exhaustive list, and a person skilled in the art may make othermodifications while nonetheless remaining within the scope of thepresent technology. Further, where no examples of modifications havebeen set forth, it should not be interpreted that no modifications arepossible and/or that what is described is the sole manner ofimplementing that element of the present technology.

Moreover, all statements herein reciting principles, aspects, andimplementations of the present technology, as well as specific examplesthereof, are intended to encompass both structural and functionalequivalents thereof, whether they are currently known or developed inthe future. Thus, for example, it will be appreciated by those skilledin the art that any block diagrams herein represent conceptual views ofillustrative circuitry embodying the principles of the presenttechnology. Similarly, it will be appreciated that any flowcharts, flowdiagrams, state transition diagrams, pseudo-code, and the like representvarious processes which may be substantially represented incomputer-readable media and so executed by a computer or processor,whether or not such computer or processor is explicitly shown.

Referring to FIGS. 1-7, terms 1, attributes 2 and data 3 areillustrated.

The DBMS and the database are stored on a server and are accessible by auser via the Internet through a Web-interface, however the system mayalso be used locally on the user PC.

After registration in the system by using the Internet and a browserinstalled on the standard PC, the user will receive an authorizedprofile with access to the database management. The user, its profileand its data access restrictions are described in the same database bymeans of the declared system.

FIGS. 2 and 3 show the table representation of the data array filled bythe user and in which the

Client

,

Meetings

and

Contract

are the terms 1, the names

Client

,

Category

,

Phone

,

Contract

, etc. are the attributes 2 of terms 1, the cells of the table containthe data 3.

The main problem of information systems is the rising price of theirmaintenance in case the system complexity is increase of the complexityof the system with the development and maintenance costs risingexponentially (see FIG. 8). There are two main risk factors:imperfection of developing a program code and compromise when choosing adatabase architecture. The present technology allows the user toindependently set the structure of data of any complexity and rules oftheir processing without the necessity of making tables, indexes, storedprocedures and functions, as well as program code. Therefore, there isno reason to contact the most expensive developing team: analyst,leading developer, programmer/coder, tester and implementer. The systemand method use the ready-made program code and architecture decision inthe form of a limited set of simple units from which an informationsystem of any complexity can be made; it also contributes to the systemversatility, in which the dependence of costs for maintenance on thesystem complexity will be as good as linear. This advantage is providedby the specified calculations and data redundancy, because the systemindexes all storage data; however, however, these costs are well belowthe time expenditures and material costs for developing teammaintenance. The main risk is the human factor when designing andprogram code and database implementation, and this risk is completelyexcluded.

The user has all means for adding, selecting, altering and deleting datawhich are accessible in any sphere of the application programming. Thesystem allows to create various templates and user interface forms,filling it by data, selected by various rules, altering data and savingit in the database, and consequently generating the interface and loginof application program without resorting to programming.

In other words, the declared system and method are completed means ofapplication of software developing.

FIG. 4 shows the fields of the types reference editor which allows theuser to set the datatypes and their attributes (characteristics), thusgenerating aspecific hierarchy of data for each specified situation onthe base of the single table of the stated system. The user sees alldatatypes of the system, as well as their dependencies and relations. Inparticular, the user sees that the

Client

type has the attributes

Phone

,

Category

and

Meetings

. At that, the

Category

is the reference value which is defined by the link on the record in the

Category

reference; the

Meetings

is a slave records array. The present technology allows to represent allof this to the user without expanding technical details, the useroperates only by the terms of his/her own business and by two simplemnemonics: the link prefix of reference

-->

and a base datatype (DATE, CHARS, NUMBER, etc.). A competent MicrosoftExcel user has enough skill for working with the types' referenceasnowadays this level of competence is common among most officeemployees.

FIG. 5 shows a correspondence between the editor's fields and the fieldsof the table representation. The types' editor allows creation theunderstandable to user representation of business-entities in form oftables. The user can set the order of column's sequence in the table(the sign

{circumflex over ( )}

in the types' editor moves an attribute one row above) and set theattributes of type are required to fill (the note of exclamation inbrackets

[!]

means that this attribute is required to fill). The structure is set inthe types' editor is shown by correspond way on tables of the referenceof the present technology.

FIGS. 6 and 7 show the form of report generation and its viewcorrespondingly. The report building involves selection of variousnumber of the report's columns from all accessible set of types. Thesystem allows selecting linked types only, at that it is not requiredfrom the user to point out how it is wanted to link the typesselected—the system will do it automatically by using the relations arespecified in the types' editor by means of links and slave arrays. Thereports' builder functionality allows implementation the main functionsof selecting, filtering and aggregation of data which exist in the SQLlanguage, including embedded reports. Also, it can be used the allembedded functions of the relational database of the system when reportsbuilding.

There are the next meanings of the fields for the

Columns

table of the report.

Name in report—name of a column in the output report, value of thereport's Column as default.

Formula—it sets a calculated expression or pseudonym of a column. Thedrop-down list of the report's columns contains the

Calculated value on the last position. It is synthetical field whichallows inserting various operators and functions available in the SQLlanguage. At that, it is permissible to operate by other report'scolumns if they have pseudonyms in the Formula field.

If the Formula field has an expression in brackets, then the system willtry finding the correspond report and using the data from it as fromembedded report.

Value (from), Value (to)—the range of values (for dates and numbers) orthe mask (for text). It is allow to use here the value of other report'sfields, if enclosing in brackets theirs name from the Formula's column.

Function—the aggregation function is applied to the field's value: AVG(average), COUNT (count), MAX (maximum), MIN (minimum), SUM (summary)The grouping of values calculated by this function is performing by allfields in which the aggregation is not used (one of listed functions isnot specified).

Function (from), Function (to)—the range of values (for dates andnumbers) or the mask (for text) is applied after calculating offunctions are selected in the Function's field (the HAVING key analoguein the SQL). It is allow to use here the value of other report's fields,if enclosing in brackets theirs name from the Formula's column.

Hide—if selected, then the correspond column will be not shown in thereport, although its value can be used for calculations, filtering andsorting of the report.

Format—the final format for a field displaying. It serves for conversionof value to required form.

Sort.—the pointer of sequence and direction of the report sorting. Thenegative number will result the return sorting of the report (decreasingof values).

Total—the aggregation function is applied to the report's column values.If a function is specified at least in one column, then the report willshow the total line with correspond values.

Embodiments of the present technology allow organizing an individualdatabase for each case which will be reliable and based on a universalsystem in understandable form for the user.

It should be expressly understood that not all technical effectsmentioned herein need to be enjoyed in each and every embodiment of thepresent technology. For example, embodiments of the present technologymay be implemented without the user enjoying some of these technicaleffects, while other embodiments may be implemented with the userenjoying other technical effects or none at all.

Modifications and improvements to the above-described implementations ofthe present technology may become apparent to those skilled in the art.The foregoing description is intended to be exemplary rather thanlimiting. The scope of the present technology is therefore intended tobe limited solely by the scope of the appended claims.

1. An electronic database, the electronic database comprising databaseelements being organized in a single table, the single table comprising:at least four columns, the at least four columns including: a firstcolumn for storing identification numbers of the database elements, asecond column for storing numbers of a parent element for the databaseelements being dependent from other database elements, a third columnfor storing database elements values, a fourth column for storing in-usedatatypes codes; and at least five rows, the at least five rowsincluding: a first row representing a root element, a second rowrepresenting a datatype, a third representing a term, a fourth rowrepresenting the term's attribute, a fifth row representing data.
 2. Theelectronic database of claim 1, wherein the single table furthercomprises a fifth column, the fifth column for storing sequence numbersof elements among elements with equal dependencies.
 3. A method forgenerating an electronic database by a database management system, themethod executable by an electronic device, the method comprising thesteps of: organizing, by the database management system, data in asingle table of at least four columns and at least five rows; generatinga first row representing a root element wherein a first column is forstoring a first identification number; generating a second rowrepresenting a datatype, wherein the first column is for storing adatatype unique identification number, the datatype uniqueidentification number being different from the first identificationnumber, a third column is for storing an in-use datatype name and afourth column is for storing a datatype code; generating a third rowrepresenting a term, wherein the first column is for storing a termunique identification number, the third column is for storing a termname and the fourth column is for storing an in-use datatype code;generating a fourth row representing a term attribute, wherein the firstcolumn is for storing a term attribute's unique identification numberand the second column is for storing a term attribute's parent elementidentification number, the term attribute being dependent on the parentelement; and generating a fifth row representing data, wherein the firstcolumn is for storing a data unique identification number, the secondcolumn is for storing a data parent element identification number, thedata being dependent on the parent element, the third column is forstoring the data and the fourth column is for storing a unique datatypecode.
 4. The method of claim 3, further comprising generating a fifthcolumn, the fifth column for storing sequence numbers of elements amongelements of equal dependencies.